They support the different character encoding capabilities of older and newer versions of Windows.

In the WinMerge menu, click Edit → Options. In the Options window General page, deselect (uncheck) the option, Disable Splash Screen.

Browse in the folder contents to the folder you want to compare. Do not select any of the files or subfolders, just click Open when Folder Selection is displayed in the File name field. If you already selected a files or subfolders, just type a random string in the File name field and click Open. If the file name you enter is not found, WinMerge opens the folder.

Unfortunately not. We recognize that it would be a good feature, but have no plans to implement it in near future. You can work around this limitation somewhat by using two WinMerge instances, or by using a third path parameter on the command line. See Command line for more information.

Not currently. If somebody wants to help with cross-platform support (using wxWidgets, for example) we are interested, of course.

Providing an integration with CVS is of questionable value because there already are so many good CVS clients. However, WinMerge does provide an integration with the diff function of one of those clients, TortoiseCVS (as described in Version control integration). Also, WinMerge can resolve conflict files (see Resolving conflict files).

MRU is an abbreviation for “Most Recently Used”, and refers to the history lists in the Select Files or Folders dialog. The list contain the last twenty paths used on each side.

OpenOffice files are archives. To be able to open them in WinMerge, you have to configure archive support:

This is because WinMerge always uses the Quick Contents file compare method for large files. This method enables WinMerge to compare large files more efficiently. To test if this is causing the behavior you're seeing, you can try raising the Quick Contents threshold for large files. See the discussion of this method in Starting a folder compare operation to learn how.

These files are plugins written with Visual Basic (6.0). The WinMerge installer does not contain Visual Basic runtime files, so those plugins cannot be loaded. You can address the problem using one of these options:

When installing WinMerge from an archive (zip or 7z) file, you also need the runtime package containing those files. See the Installing from an archive in the installation Help topic for details.

Maybe your files have different line ending styles (for example, Windows and Unix). By default, WinMerge compares line ending styles. To disable it, click Edit → Options. In the Compare page, enable (check) the option, Ignore carriage return differences.

Try clicking View → Select Font and selecting a different font.

This is what we call a lossy conversion.

For Unicode files (UCS-2, UTF-8), use WinMergeU.exe.

For ANSI files, this is probably due to code-page problems. To troubleshoot, click Edit → Options. Then in the Codepages page, see if the option Detect codepage info is checked. If it is, deselect the option, click OK, and see if that helps.

Unfortunately, WinMerge supports only non-proportional fonts.

When Automatic Rescan is enabled (in the Editor page of Options), WinMerge delays rescanning while you edit files. That is, no rescanning occurs until shortly after you stop typing. Without this delay, WinMerge would rescan after every typed character, making the editing process too slow. The delay especially improves editing bigger files, which can take several seconds to rescan.

Yes, there is basic printing support: click File → Print.

No, you can't. Many users have requested this feature but we don't have any plans to implement it. We don't believe it would really improve usability.

Open WinMerge from the command line, and include the -e switch.

Use the -x command line switch.

Have your external program invoke WinMerge with the /ub option, which tells WinMerge to not add the files to the MRU.

Create a batch file that contains one of these lines (but not both):

Call this batch file from your program.

You might have one of these problems:

Perry-style patches are zip files containing original and changed files in different directories. WinMerge has internal support (surprise!) for handling these files: just launch a compare operation, selecting the zip file for both the left and right sides. WinMerge opens the contents of the zip file in a Folder Compare window, comparing the original and changed files.

Unfortunately WinMerge can only use 7-zip.

Yes: click the Options button (or click Edit → Options). In the Archive Support page, enable the Detect archive type from file signature option.

Open the file in Windows Notepad (for example, click Start → (All) Programs → Accessories → Notepad). Click File → Save As, and in the Save As dialog, scroll to the Encoding item at the dropdown list. The possible values include:

No. It might be added in later versions. Until then, you can use the Win32 port of diffutils. The latest version of diffutils (and patch) can be downloaded from the SourceForge GnuWin32 project page: http://sourceforge.net/projects/gnuwin32.

No. However, you can apply patches using the patch tool from the GnuWin32 project, because WinMerge produces patch files that are compatible with GNU/diffutils. Also, see the preceding question.